Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

3.0.4 #135

Merged
merged 3 commits into from
Jul 26, 2019
Merged

3.0.4 #135

merged 3 commits into from
Jul 26, 2019

Conversation

davimacedo
Copy link
Member

No description provided.

@davimacedo davimacedo requested review from acinader and dplewis July 26, 2019 17:55
@codecov
Copy link

codecov bot commented Jul 26, 2019

Codecov Report

Merging #135 into master will not change coverage.
The diff coverage is n/a.

Impacted file tree graph

@@          Coverage Diff          @@
##           master   #135   +/-   ##
=====================================
  Coverage     100%   100%           
=====================================
  Files           5      5           
  Lines         266    266           
=====================================
  Hits          266    266

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 175c261...c4a7f16. Read the comment docs.

Copy link
Contributor

@TomWFox TomWFox left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Changelog looks good, I believe you need to run npm install to update the package-lock.json

@davimacedo
Copy link
Member Author

@TomWFox just done. Can you please take a look again?

Copy link
Contributor

@TomWFox TomWFox left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good to me 👍

@davimacedo davimacedo merged commit 1deb912 into master Jul 26, 2019
@TomWFox TomWFox deleted the 3.0.4 branch July 26, 2019 18:38
@funkenstrahlen
Copy link
Contributor

Awesome! Thanks for the new release!

@funkenstrahlen
Copy link
Contributor

Are you able to push the new release to the npm package directory? Currently it does not know about all of the last releases: https://www.npmjs.com/package/@parse/push-adapter

@davimacedo
Copy link
Member Author

Yes.. that's what I am trying to do for a while. Travis is supposed to publish it but it is failing. I am trying to figure it out.

@davimacedo
Copy link
Member Author

@funkenstrahlen finally we have a new version released in npm. Parse Server should have it automatically updated in the next few hours as well.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants